System and method for providing secure subnet management agent (sma) in an infiniband (ib) network

ABSTRACT

A system and method can provide a secure subnet management agent (SMA) in an Infiniband (IB) network. The system can comprise a host channel adapter (HCA) associated with a host, wherein the HCA operates to implement a SMA in its embedded firmware. The HCA can prevent a host administrator or software with root access to the host from changing the embedded firmware on the HCA and modifying one or more states associated with the SMA without being endorsed by a site administrator. Additionally, the SMA is associated with a management key, and the host is not allowed to observe the management key without being endorsed by a site administrator.

CLAIM OF PRIORITY

This application claims the benefit of priority on U.S. Provisional Patent Application No. 61/493,330, entitled “STATEFUL SUBNET MANAGER FAILOVER IN A MIDDLEWARE MACHINE ENVIRONMENT” filed Jun. 3, 2011, which application is herein incorporated by reference.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to the following patent application, which is hereby incorporated by reference in its entirety:

-   -   U.S. patent application Ser. No. ______, titled “SYSTEM AND         METHOD FOR PROVIDING SECURE SUBNET MANAGEMENT AGENT (SMA) BASED         FENCING IN AN INFINIBAND (IB) NETWORK”, inventors Bjørn-Dag         Johnsen, Line Holen and Dag Georg Moxnes, filed ______ (Attorney         Docket No.: ORACL-05379US0).

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

FIELD OF INVENTION

The present invention is generally related to computer systems, and is particularly related to supporting an InfiniBand (IB) network.

BACKGROUND

The interconnection network plays a beneficial role in the next generation of super computers, clusters, and data centers. High performance network technology, such as the InfiniBand (IB) technology, is replacing proprietary or low-performance solutions in the high performance computing domain, where high bandwidth and low latency are the key requirements. For example, IB installations are used in supercomputers such as Los Alamos National Laboratory's Roadrunner, Texas Advanced Computing Center's Ranger, and Forschungszcntrum Juelich's JuRoPa.

IB was first standardized in October 2000 as a merge of two older technologies called Future I/O and Next Generation I/O. Due to its low latency, high bandwidth, and efficient utilization of host-side processing resources, it has been gaining acceptance within the High Performance Computing (HPC) community as a solution to build large and scalable computer clusters. The de facto system software for IB is OpenFabrics Enterprise Distribution (OFED), which is developed by dedicated professionals and maintained by the OpenFabrics Alliance. OFED is open source and is available for both GNU/Linux and Microsoft Windows.

SUMMARY

Described herein is a system and method that can provide a secure subnet management agent (SMA) in an Infiniband (IB) network. The system can comprise a host channel adapter (HCA) associated with a host, wherein the HCA operates to implement a SMA in its embedded firmware. The HCA can prevent a host administrator or software with root access to the host from changing the embedded firmware on the HCA and modifying one or more states associated with the SMA without being endorsed by a site administrator. Additionally, the SMA is associated with a management key, and the host is not allowed to observe the management key without being endorsed by a site administrator.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows an illustration of a fabric model in a middleware environment in accordance with an embodiment of the invention.

FIG. 2 shows an illustration of a HCA implementation in accordance with an embodiment of the invention.

FIG. 3 shows an illustration of supporting a password based HCA firmware upgrade in accordance with an embodiment of the invention.

FIG. 4 shows an illustration of supporting an upgrade control executable in accordance with an embodiment of the invention.

FIG. 5 shows an illustration of supporting secure firmware upgrade in an automated management solution in accordance with an embodiment of the invention.

FIG. 6 shows an illustration of supporting a encrypted firmware image based HCA firmware upgrade in accordance with an embodiment of the invention.

FIG. 7 illustrates an exemplary flow chart for providing a secure subnet management agent (SMA) in an IB network in accordance with an embodiment of the invention.

DETAILED DESCRIPTION

Described herein is a system and method that can provide a secure subnet management agent (SMA) in a middleware machine environment.

FIG. 1 shows an illustration of a fabric model in a middleware environment in accordance with an embodiment of the invention. As shown in FIG. 1, an interconnected network, or a fabric 100, can include switches 101-103, bridges and routers 104, host channel adapters (HCAs) 105-106 and designated management hosts 107. Additionally, the fabric can include, or be connected to, one or more hosts 108 that are not designated management hosts.

The designated management 107 hosts can be installed with HCAs 105, 106, a network software stack and relevant management software in order to perform network management tasks. Furthermore, firmware and management software can be deployed on the switches 101-103, and the bridges and routers 104 to direct traffic flow in the fabric. Here, the host HCA drivers, OS and Hypervisors on hosts 108 that are not designated management hosts may be considered outside the scope of the fabric from a management perspective.

The fabric 100 can be in a single media type, e.g. an IB only fabric, and be fully connected. The physical connectivity in the fabric ensures in-band connectivity between any fabric components in the non-degraded scenarios. Alternatively, the fabric can be configured to include Ethernet (Enet) connectivity outside gateway (GW) external ports on a gateway 109. Additionally, it is also possible to have independent fabrics operating in parallel as part of a larger system. For example, the different fabrics can only be indirectly connected via different HCAs or HCA ports.

InfiniBand (IB) Architecture

IB architecture is a serial point-to-point technology. Each of the IB networks, or subnets, can include a set of hosts interconnected using switches and point-to-point links. A single subnet can be scalable to more than ten-thousand nodes and two or more subnets can be interconnected using an IB router. The hosts and switches within a subnet are addressed using local identifiers (LIDs), e.g. a single subnet may be limited to 49151 unicast addresses.

An IB subnet can employ at least one subnet manager (SM) which is responsible for initializing and starting up the sub-net including the configuration of all the IB ports residing on switches, routers and host channel adapters (HCAs) in the subset. The SM's responsibility also includes routing table calculation and deployment. Routing of the network aims at obtaining full connectivity, deadlock freedom, and load balancing between all source and destination pairs. Routing tables can be calculated at network initialization time and this process can be repeated whenever the topology changes in order to update the routing tables and ensure optimal performance.

At the time of initialization, the SM starts in the discovering phase where the SM does a sweep of the network in order to discover all switches and hosts. During the discovering phase, the SM may also discover any other SMs present and negotiate who should be the master SM. When the discovering phase is completed, the SM can enter a master phase. In the master phase, the SM proceeds with LID assignment, switch configuration, routing table calculations and deployment, and port configuration. At this point, the subnet is up and ready to use.

After the subnet is configured, the SM can monitor the network for changes (e.g. a link goes down, a device is added, or a link is removed). If a change is detected during the monitoring process, a message (e.g. a trap) can be forwarded to the SM and the SM can reconfigure the network. Part of the reconfiguration process, or a heavy sweep process, is the rerouting of the network which can be performed in order to guarantee full connectivity, deadlock freedom, and proper load balancing between all source and destination pairs.

The HCAs in an IB network can communicate with each other using queue pairs (QPs). A QP is created during the communication setup, and a set of initial attributes such as QP number, HCA port, destination LID, queue sizes, and transport service are supplied. On the other hand, the QP associated with the HCAs in a communication is destroyed when the communication is over. An HCA can handle many QPs, each QP consists of a pair of queues, a send queue (SQ) and a receive queue (RQ). There is one such pair present at each end-node that is participating in the communication. The send queue holds work requests to be transferred to the remote node, while the receive queue holds information on what to do with the data received from the remote node. In addition to the QPs, each HCA can have one or more completion queues (CQs) that are associated with a set of send and receive queues. The CQ holds completion notifications for the work requests posted to the send and receive queue.

The IB architecture is a flexible architecture. Configuring and maintaining an IB subnet can be carried out via special in-band subnet management packets (SMPs). The functionalities of a SM can, in principle, be implemented from any node in the IB subnet. Each end-port in the IB subnet can have an associated subnet management agent (SMA) that is responsible for handling SMP based request packets that are directed to it. In the IB architecture, a same port can represent a SM instance or other software component that uses SMP based communication. Thus, only a well defined sub-set of SMP operations can be handled by the SMA.

SMPs use dedicated packet buffer resources in the fabric, e.g. a special virtual lane (VL15) that is not flow-controlled (i.e. SMP packets may be dropped in the case of buffer overflow. Also, SMPs can use either the routing that the SM sets up based on end-port Local Identifiers (LIDs), or SMPs can use direct routes where the route is fully defined by the sender and embedded in the packet. Using direct routes, the packet's path goes through the fabric in terms of an ordered sequence of port numbers on HCAs and switches.

The SM can monitor the network for changes using SMAs that are presented in every switch and/or every HCA. The SMAs communicate changes, such as new connections, disconnections, and port state change, to the SM using traps and notices. A trap is a message sent to alert end-nodes about a certain event. A trap can contain a notice attribute with the details describing the event. Different traps can be defined for different events. In order to reduce the unnecessary distribution of traps, IB applies an event forwarding mechanism where end-nodes are required to explicitly subscribe to the traps they want to be informed about.

The subnet administrator (SA) is a subnet database associated with the master SM to store different information about a subnet. The communication with the SA can help the end-node to establish a QP by sending a general service management datagram (MAD) through a designated QP, e.g. QP1. Both sender and receiver require information such as source/destination LIDs, service level (SL), maximum transmission unit (MTU), etc. to establish communication via a QP. This information can be retrieved from a data structure known as a path record that is provided by the SA. In order to obtain a path record, the end-node can perform a path record query to the SA, e.g. using the SubnAdmGet/SubnAdmGetable operation. Then, the SA can return the requested path records to the end-node.

The IB architecture provides partitions as a way to define which IB end-ports should be allowed to communicate with other IB end-ports. Partitioning is defined for all non-SMP packets on the IB fabric. The use of partitions other than the default partition is optional. The partition of a packet can be defined by a 16 bit P_Key that consists of a 15 bit partition number and a single bit member type (full or limited).

The partition membership of a host port, or an HCA port, can be based on the premise that the SM sets up the P_Key table of the port with P_Key values that corresponds to the current partition membership policy for that host. In order to compensate for the possibility that the host may not be fully trusted, the IB architecture also defines that switch ports can optionally be set up to do partition enforcement. Hence, the P_Key tables of switch ports that connect to host ports can then be set up to reflect the same partitions as the host port is supposed to be a member of (i.e. in essence equivalent to switch enforced VLAN control in Ethernet LANs).

Since the IB architecture allows full in-band configuration and maintenance of an IB subnet via SMPs, the SMPs themselves are not subject to any partition membership restrictions. Thus, in order to avoid the possibility that any rough or compromised node on the IB fabric is able to define an arbitrary fabric configuration (including partition membership), other protection mechanisms are needed.

M_Keys can be used as the basic protection/security mechanism in the IB architecture for SMP access. An M_Key is a 64 bit value that can be associated individually with each individual node in the IB subnet, and where incoming SMP operations may be accepted or rejected by the target node depending on whether the SMP includes the correct M_Key value (i.e. unlike P_Keys, the ability to specify the correct M_Key value—like a password—represents the access control).

By using an out-of-band method for defining M_Keys associated with switches, it is possible to ensure that no host node is able to set up any switch configuration, including partition membership for the local switch port. Thus, an M_Key value is defined when the switch IB links becomes operational. Hence, as long as the M_Key value is not compromised or “guessed” and the switch out-of-band access is secure and restricted to authorized fabric administrators, the fabric is secure.

Furthermore, the M_Key enforcement policy can be set up to allow read-only SMP access for all local state information except the current M_Key value. Thus, it is possible to protect the switch based fabric from un-authorized (re-)configuration, and still allow host based tools to perform discovery and diagnostic operations.

The flexibility provided by the IB architecture allows the administrators of IB fabrics/subnets, e.g. HPC clusters, to decide whether to use embedded SM instances on one or more switches in the fabric and/or set up one or more hosts on the IB fabric to perform the SM function. Also, since the wire protocol defined by the SMPs used by the SMs is available through APIs, different tools and commands can be implemented based on use of such SMPs for discovery, diagnostics and are controlled independently of any current Subnet Manager operation.

From a security perspective, the flexibility of IB architecture indicates that there is no fundamental difference between root access to the various hosts connected to the IB fabric and the root access allowing access to the IB fabric configuration. This is fine for systems that are physically secure and stable. However, this can be problematic for system configurations where different hosts on the IB fabric are controlled by different system administrators, and where such hosts should be logically isolated from each other on the IB fabric.

Secure HCA SMA Implementation

In accordance with an embodiment of the invention, an HCA can implement a SMA, and the run-time and persistent state information associated with the SMA, in a way that is isolated from a host that is connected to the HCA. Additionally, the host administrators, which have root access at the hypervisor or physical OS level, can perform host software and firmware updates and upgrades on the local HCAs as part of standard procedures for maintaining and updating software and firmware on the physical hosts. There can be no need for special procedures for ensuring fabric integrity.

FIG. 2 shows an illustration of an HCA implementation in accordance with an embodiment of the invention. As shown in FIG. 2, an HCA 201 is associated with a host 202 in a fabric 200. The host 202 can include an operating system (OS) 206 and host stacks 207. The HCA 201 can implement a SMA 203 completely in a HCA embedded firmware 204, and make sure that no access from the host 202, e.g. via a peripheral component interconnect express (PCIe) connection 210, can modify any state or observe a management key, e.g. the currently defined M_Key 205.

Furthermore, in order to allow field upgrade of HCA firmware 204, the system can ensure that the host administrators 211 and/or the software that has root access to the host are not able to change the firmware image 204 without being endorsed by the site administrator 212. This can prevent malicious viruses from potentially changing the firmware image.

This protection scheme can ensure that a host administrator 211 is not able to cause damage to the fabric configuration by starting a host based SM 221 by mistake. Also, this protection scheme can prevent an unauthorized SM from configuring both the switches and the designated SMs to use an M_Key 205 value with minimal protection level, e.g. via a SMP 220.

FIG. 3 shows an illustration of supporting a password-based HCA firmware upgrade in accordance with an embodiment of the invention. As shown in FIG. 3, a site administrator 312, or a fabric administrator, can use a password mechanism to upgrade an embedded firmware 304 on an HCA 301 that is connected to a host 302. This password mechanism allows the actual password 321 to be securely stored and maintained, e.g. in an HCA persistent storage 320. Additionally, this password mechanism can be combined with other mechanisms such as verifying the checksum of the installed firmware image.

This password mechanism can prevent the host 302, and the OS 306 and the host stacks 307 on the host 302, from taking control of the password 321. As shown in FIG. 3, the site administrator 312 can be allowed to have root access to the various physical hosts, e.g. the host 302, and, is, thereby, allowed to perform a password based upgrade on behalf of the host administrator 311 without giving the host administrator 311 an access to the HCA password 321.

Furthermore, the password mechanism can be used together with other mechanisms to address the concern when it is not acceptable or possible to give the site/fabric administrator 312 root accesses to the host 302. Also, this approach can involve complicated procedures because the host administrator 311 may not fully control the maintenance of the local host system 302, and may be prevented from using the existing automated upgrade procedures.

Also, the password mechanism can be used together with other mechanisms to address the security issues associated with this approach, e.g. a communication session with the host 302 for performing the password based HCA firmware upgrade can potentially be subject to spyware or other malicious software that could compromise the HCA password 321, since the host OS 306 and networking stack 307 are controlled by the host administrator 311 and not by the site administrator 312.

Additionally, the SMA 303, M_key 305 and PCIe 310, as shown in FIG. 3, have the same structure and perform the same function as the SMA 203, M_key 205 and PCIe 210, as shown in FIG. 2.

FIG. 4 shows an illustration of supporting an upgrade control executable in accordance with an embodiment of the invention. As shown in FIG. 4, an upgrade control executable 405 can be used to upgrade an embedded firmware 404 for an HCA 401 that is connected to a host 402. This upgrade control executable 405, which contains encrypted versions of HCA passwords 420, can be bundled with the HCA firmware 404 distribution. This HCA password 420 can be a site specific password configured by the site administrator 412.

The upgrade control executable 405 can be used in host administrator 411 controlled, potentially automated, upgrade procedures. This approach avoids the need for the site administrator 412 to have root access to the host 402. Furthermore, the upgrade control executable 405 can be used to together with other mechanisms to avoid the risk of spyware on the host 402, since the host OS 406 and networking stack 407 are controlled by the host administrator 411 and not by the site administrator 412.

Additionally, the SMA 403 and PCIe 410, as shown in FIG. 4, have the same structure and perform the same function as the SMA 203 and PCIe 210, as shown in FIG. 2.

FIG. 5 shows an illustration of supporting secure firmware upgrade in an automated management solution in accordance with an embodiment of the invention. As shown in FIG. 5, an external management application 520, e.g. the Enterprise Management Operations Center (EM-OC) provided by Oracle, can be used to upgrade an embedded firmware 504 for an HCA 501 that is connected to a host 502, as part of an automated management solution, without depending on the host OS 506 and networking stack 507.

A special host boot image 505 defined by the external management application 520 can be installed on the host 502, and can be used in the automated management solution for upgrading device firmware 504 on servers. The special host boot image 505 can execute on the host 502 under the complete control of the site/fabric administrator 512, i.e. the host administrator 511 may not be allowed to have access to the host 502 after the special host boot image 505 is installed.

Using this approach, the site administrator 511 can invoke the external management application 520 based automated upgrade procedures and can give the external management application 520 permission, over the network, to install the special host boot image 505 on host 502 and then install firmware 504 on the HCA 501. This special host boot image 505 can be provided with site specific configuration (e.g. by a site administrator 512) that includes specific parameters for identifying the various images that the upgrade operation may include.

The special host boot image 505 can include its own access control and authentication mechanisms that can prevent tampering from the host administrator 511 and/or other non-authorized humans or software. In the process of the secure HCA firmware upgrade, the special host boot image 505 can be used in a manner similar to the upgrade control executable 305 as described above and shown in FIG. 3. The special host boot image 505 can further contain both a list of passwords, which includes old passwords that have been used previously in this site and a new password that can be installed along with the specified upgrade. Thus, the automated upgrade can use the list of passwords to upgrade multiple hosts that represent different HCA password generation.

Additionally, the SMA 503 and PCIe 510, as shown in FIG. 5, have the same structure and perform the same function as the SMA 203 and PCIe 210, as shown in FIG. 2.

FIG. 6 shows an illustration of supporting a encrypted firmware image based HCA firmware upgrade in accordance with an embodiment of the invention. As shown in FIG. 6, a site administrator 612, or a fabric administrator, can use an encrypted firmware image 614 to upgrade an embedded firmware 604 on a HCA 601 that is connected to a host 602. A built-in decryption mechanism can be provided for the HCA 601 to ensure that the installed firmware image 604 is valid. The built-in decryption mechanism can be associated with embedded decryption parameter 621 that are securely stored and maintained, e.g. in an HCA persistent storage 320 at the factory, or updated via special secure procedures by the site administrator 612 prior to enabling the HCA 601 to be used in production in the data center.

Additionally, if the initial firmware image 304 supports in-band authentication, then the actual upgrade procedure may be protected as long as the built-in authentication mechanism is not compromised and no new firmware 614 can be installed without resetting the link on all local HCA ports. By resetting the link on all local HCA ports, an external SM 615 can be guaranteed to observe a reset link state on the corresponding switch port and then to perform rediscovery and re-authentication.

This scheme can also include that no upgradable firmware or any software-based procedure can change the persistent hardware GUID of the HCA 601 that any legal and authenticated firmware image may report.

The site administrator can make sure that the GUID of a HCA 601 is correctly recorded and that the initial firmware image 604 is secure prior to allowing the HCA 601 to be used in any host 602 that can be controlled by any administrator 611 or software with host level root access but without fabric/site administrator privileges.

Thus, the HCA firmware 604 can be upgraded in-band from the fabric instead of relying on the host based PCIe 610 based upgrade, with the support of a secure fabric, a proper initial secure state for the HCA firmware 604, and in-band authentication mechanisms.

In accordance with an embodiment of the invention, the identity and trustfulness of the HCA 601 hardware and firmware 604 can be authenticated in-band by a SM 615 using discovery or public/private key based schemes. Furthermore, the integrity of a new firmware image is ensured when the image is encrypted using the public/private based key scheme, and/or via an encryption password scheme. The encryption password scheme can use an encryption password that is either pre-defined for the HCA 601, or supplied via the public/private based key scheme.

FIG. 7 illustrates an exemplary flow chart for providing a secure subnet management agent (SMA) in an IB network in accordance with an embodiment of the invention. As shown in FIG. 7, at step 701, an HCA can be associated with a host, wherein the HCA operates to implement a SMA in its embedded firmware. Then, at step 702, the HCA can prevent a host administrator and/or software with root access to the host from changing the embedded firmware on the HCA and modifying one or more states associated with the SMA without being endorsed by a site administrator. Additionally, at step 703, the SMA can be associated with a management key and the host is not allowed to observe the management key without being endorsed by a site administrator.

The present invention may be conveniently implemented using one or more conventional general purpose or specialized digital computer, computing device, machine, or microprocessor, including one or more processors, memory and/or computer readable storage media programmed according to the teachings of the present disclosure. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art.

In some embodiments, the present invention includes a computer program product which is a storage medium or computer readable medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the present invention. The storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.

The foregoing description of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to the practitioner skilled in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalence. 

1. A system for providing secure subnet management agent (SMA) in an Infiniband (IB) fabric, comprising: a host channel adapter (HCA) associated with a host, wherein the HCA operates to implement a SMA in its embedded firmware, and wherein the HCA prevents a host administrator or software with root access to the host from changing the embedded firmware on the HCA and modifying one or more states associated with the SMA without being endorsed by a site administrator.
 2. The system according to claim 1, wherein: the SMA is associated with a management key, and the host is not allowed to observe the management key without being endorsed by a site administrator.
 3. The system according to claim 1, wherein: the host can access the HCA via a peripheral component interconnect express (PCIe) connection.
 4. The system according to claim 1, wherein: a site administrator is allowed to upgrade the embedded firmware on the HCA using a password mechanism, wherein the site administrator is allowed to have root access to the host.
 5. The system according to claim 1, wherein: an upgrade of the HCA firmware is allowed to take place in-band via the IB fabric.
 6. The system according to claim 5, wherein: identity and trustfulness of the HCA hardware and firmware can be authenticated in-band by a subnet manager using discovery or public/private key based schemes, and integrity of a new firmware image is ensured when the image is encrypted using the public/private based key scheme, and/or via an encryption password scheme where the encryption password is either pre-defined for the HCA, or supplied via the public/private based key scheme.
 7. The system according to claim 1, further comprising: a host administrator is allowed to use an upgrade control executable with encrypted versions of HCA passwords to upgrade the embedded firmware on the HCA, wherein the encrypted versions of HCA passwords are configured with site specific passwords by a site administrator.
 8. The system according to claim 1, further comprising: an external management application that supports upgrading the embedded firmware on the HCA using a special host boot image, wherein the special host boot image is defined by the external management application and includes site specific configuration by a site administrator.
 9. The system according to claim 8, wherein: the special host boot image includes its own access control and authentication mechanisms that can prevent tampering from a host administrator and/or other non-authorized humans or software, or a list of passwords that can be used to upgrade multiple hosts that represent different HCA password generation.
 10. The system according to claim 1, wherein: the embedded firmware on the HCA can be upgraded using an encrypted firmware image.
 11. A method for providing secure subnet management agent (SMA) in an Infiniband (IB) network, comprising: providing a host channel adapter (HCA) associated with a host, wherein the HCA operates to implement a SMA in its embedded firmware, and preventing, via the HCA, a host administrator and/or software with root access to the host from changing the embedded firmware on the HCA and modifying one or more states associated with the SMA without being endorsed by a site administrator.
 12. The method according to claim 11, further comprising: associating the SMA with a management key, and wherein the host is not allowed to observe the management key without being endorsed by a site administrator.
 13. The system according to claim 11, further comprising: allowing the host to access the HCA via a peripheral component interconnect express (PCIe) connection.
 14. The system according to claim 11, further comprising: allowing a site administrator, which has root access to the host, to upgrade the embedded firmware on the HCA using a password mechanism.
 15. The system according to claim 1, further comprising: allowing a host administrator to use an upgrade control executable with encrypted versions of HCA passwords to upgrade the embedded firmware on the HCA, wherein the encrypted versions of HCA passwords are configured with site specific passwords by a site administrator.
 16. The system according to claim 11, further comprising: allowing an upgrade of the HCA firmware to take place in-band via the IB fabric, allowing identity and trustfulness of the HCA hardware and firmware to be authenticated in-band by a subnet manager using discovery or public/private key based schemes, and determining that integrity of a new firmware image is ensured when the image is encrypted using the public/private based key scheme, and/or via an encryption password scheme where the encryption password is either pre-defined for the HCA, or supplied via the public/private based key scheme
 17. The system according to claim 11, further comprising: providing an external management application that supports upgrading the embedded firmware on a HCA using a special host boot image, and allowing the special host boot image to be defined by the external management application and to include site specific configuration by a site administrator.
 18. The system according to claim 17, further comprising: allowing the special host boot image to include its own access control and authentication mechanisms that can prevent tampering from a host administrator and/or other non-authorized humans or software, or a list of passwords that can be used to upgrade multiple hosts that represent different HCA password generation
 19. The system according to claim 11, further comprising: using an encrypted firmware image to upgrade the embedded firmware on the HCA.
 20. A non-transitory machine readable storage medium having instructions stored thereon that when executed cause a system to perform the steps of: providing a host channel adapter (HCA) associated with a host, wherein the HCA operates to implement a SMA in its embedded firmware, and preventing, via the HCA, a host administrator and/or software with root access to the host from changing the embedded firmware on the HCA and modifying one or more states associated with the SMA without being endorsed by a site administrator. 